-
Notifications
You must be signed in to change notification settings - Fork 325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move global tracer and substitute agent-core types with API types where this is trivially possible. #3054
Conversation
👋 @raphw Thanks a lot for your contribution! It may take some time before we review a PR, so even if you don’t see activity for some time, it does not mean that we have forgotten about it. Every once in a while we go through a process of prioritization, after which we are focussing on the tasks that were planned for the upcoming milestone. The prioritization status is typically reflected through the PR labels. It could be pending triage, a candidate for a future milestone, or have a target milestone set to it. |
This is mostly auto-generated. I do however wonder about one difference, and that is the change here: main...raphw:apm-agent-java:reduce-api-exposure#diff-732acc761e4310277786f5059749ac54e3f0dcfa17d8976ca3892fa7fb7d5c52L154 This particular use of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approval to allow running on CI, thorough review will follow.
...gin/apm-jms-plugin-base/src/main/java/co/elastic/apm/agent/jms/JmsInstrumentationHelper.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few minor comments.
In addition I think the tests are currently failing and still need some attention.
...-plugins/apm-api-plugin/src/main/java/co/elastic/apm/agent/pluginapi/ApiInstrumentation.java
Outdated
Show resolved
Hide resolved
...-sdk/apm-aws-sdk-1-plugin/src/main/java/co/elastic/apm/agent/awssdk/v1/helper/SQSHelper.java
Show resolved
Hide resolved
.../src/main/java/co/elastic/apm/agent/awssdk/common/AbstractDynamoDBInstrumentationHelper.java
Show resolved
Hide resolved
...ent-plugins/apm-grpc/apm-grpc-plugin/src/main/java/co/elastic/apm/agent/grpc/GrpcHelper.java
Outdated
Show resolved
Hide resolved
...kafka-base-plugin/src/main/java/co/elastic/apm/agent/kafka/KafkaProducerInstrumentation.java
Show resolved
Hide resolved
...plugin/src/main/java/co/elastic/apm/agent/kafka/SpringKafkaBatchListenerInstrumentation.java
Outdated
Show resolved
Hide resolved
...-plugins/apm-servlet-plugin/src/main/java/co/elastic/apm/agent/servlet/ServletApiAdvice.java
Outdated
Show resolved
Hide resolved
…re this is trivially possible. This change is mainly generated by IDEA code substitution, with minor adjustments. By using API types, the dependency on implementation is reduced and the required API surface becomes more visible. This change is in preparation of removing the core module as a dependency of the internal plugins.
…code readability.
…/main/java/co/elastic/apm/agent/kafka/SpringKafkaBatchListenerInstrumentation.java Co-authored-by: Jonas Kunz <[email protected]>
…astic/apm/agent/grpc/GrpcHelper.java Co-authored-by: Jonas Kunz <[email protected]>
ee20b86
to
d5c9c4d
Compare
Tests should be fixed by now. Mainly missing mock configurations to reflect |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we are good to merge!
Side Note for the next PR: Would be great if you could use merge instead of force-push. This allows us to use the "Review changes since last review" feature from GH when doing review iterations.
Will do, I rebased to main, in hope that a mysterious test error would disappear by it, that's what the force push was about. |
run elasticsearch-ci/docs |
This change is mainly generated by IDEA code substitution, with minor adjustments. By using API types, the dependency on implementation is reduced and the required API surface becomes more visible. This change is in preparation of removing the core module as a dependency of the internal plugins.